Presentation: Tweet"Rx: your prescription to cure event processing blues"
Event-driven "reactive" programming is way too hard with today's development frameworks. The staggering amount of manual and error-prone plumbing needed to compose event sources leads to incomprehensible and hard to maintain code. As we reach out to services in the cloud, mobile programming, etc. the desire for event-oriented (asynchronous) computation is ever increasing, requiring a fresh look on the problems imposed by reactive programming. Centered around the concept of observable sequences, Rx provides a framework that takes care of the hard parts of programming event-processing systems. Instead of getting lost in the jungle of hand-crafted callbacks, you now can start dreaming about the endless possibilities of composing queries over asynchronous data sources, piggybacking on convenient LINQ syntax.
In this session, we'll cover the design philosophy of Rx, rooted in a deep connection between the pull-based (synchronous and “interactive”) IEnumerable interface and the new push-based (asynchronous and “reactive”) IObservable interface. From this core understanding, we'll start looking at exposing existing event sources through the lenses of observable sequences. Next, we explore various query operators defined over observable sequences, driving concepts home by a bunch of samples. In passing, we also get to know Rx’s abstraction for introducing concurrency, known as IScheduler. Finally, we’ll have a look at the “async” and “await” features slated for the next version of C# and VB, and explain how those relate to asynchronous programming with Rx.
Democratizing event processing, asynchronous, reactive programming starts today. Don't miss out on it!
